Merged
Conversation
Contributor
SDK Size
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 Goal
This PR standardizes several legacy UI component names to a cleaner and more consistent naming scheme. It also aligns the related public API, theme keys, tests, and sample usages with those names. It also adds a few lightweight message row customization slots so consumers can extend layout without fully replacing the default message components.
MessageSimple->MessageItemViewMessageAvatar->MessageAuthorMessageInput->MessageComposerChannelListMessenger->ChannelListViewChannelPreviewMessenger->ChannelPreviewViewMessageSpacerMessageContentTopViewMessageContentBottomViewMessageContentLeadingViewMessageContentTrailingView🛠 Implementation details
🎨 UI Changes
iOS
Android
🧪 Testing
☑️ Checklist
developbranch